build(deps): Bump tonic and prost related packages to 0.14#6276
Merged
build(deps): Bump tonic and prost related packages to 0.14#6276
Conversation
This was referenced Jan 14, 2026
incrypto32
approved these changes
Jan 22, 2026
Member
incrypto32
left a comment
There was a problem hiding this comment.
LGTM! needs a rebase though
In particular, the packages are prost, prost-types, tonic, tonic-prost, and tonic-prost-build. Unfortunately, this also requires updating arrow to 57.x It doesn't seem possible to update any of these packages individually, they are all tightly dependent on each other, and attempts at individual updates cause compilation errors.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
In particular, the packages are prost, prost-types, tonic, tonic-prost, and tonic-prost-build.
Unfortunately, this also requires updating arrow to 57.x
It doesn't seem possible to update any of these packages individually, they are all tightly dependent on each other, and attempts at individual updates cause compilation errors.